web/library: Remove worker-loader #1069
Conversation
|
Could you elaborate on the benefit to removing this? Do you feel like our assumptions here make it difficult to override this in the future? |
|
Ah good question. The reason was just that I don't think many users will be using it, and that it's another dependency that has to be downloaded and then ie: This was just a continuation of my ongoing work to slim down Neutrino 9 as much of possible compared to the accumulation of features/complexity that we'd ended up with Neutrino 8 (whose If you felt strongly about leaving it then, then happy to do so. Do you know of many projects that use web workers with Neutrino? :-) |
|
@edmorley I have in the past, which is why I had added it, since it gave a way to use workers with zero config. That said, I haven't used it in a while, and don't have a major issue removing it. My biggest concern was being able to import as worker with no config. 😄 |
|
I think in the future a combined opt-in preset for various worker types might be nice to have? (And consolidate with |
Since the top-level presets aim to cover the 80% case, and web workers are still less common. If after Neutrino 9's release there ends up being demand for them, we'd be better off having a separate opt-in preset (similar to `@neutrinojs/pwa`).
Since the top-level presets aim to cover the 80% case, and web workers are still less common. If after Neutrino 9's release there ends up being demand for them, we'd be better off having a separate opt-in preset (similar to
@neutrinojs/pwa).